Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0331bf80ededb58c5769b174a9e1f64761e662f7e8347c501127e26038924755

Tx prefix hash: 8915f980d6e72f17ccfe0c0cb1fad86c911b5c4d27497a111a58e5049f039f75
Tx public key: fd41dd408f38885fde7d7c2ff864c9b0a62a52437ff5217e4b8a60036f1174e0
Timestamp: 1673059912 Timestamp [UCT]: 2023-01-07 02:51:52 Age [y:d:h:m:s]: 02:092:11:02:42
Block: 669253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587771 RingCT/type: yes/0
Extra: 01fd41dd408f38885fde7d7c2ff864c9b0a62a52437ff5217e4b8a60036f1174e002110000000152542ceb000000000000000000

1 output(s) for total of 3.719520436000 dcy

stealth address amount amount idx
00: 3d8e056d2233324e6693fe66e2ed9d1b42a61d4f4eaab27e26a158a62e2781d2 3.719520436000 1110556 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 669263, "vin": [ { "gen": { "height": 669253 } } ], "vout": [ { "amount": 3719520436, "target": { "key": "3d8e056d2233324e6693fe66e2ed9d1b42a61d4f4eaab27e26a158a62e2781d2" } } ], "extra": [ 1, 253, 65, 221, 64, 143, 56, 136, 95, 222, 125, 124, 47, 248, 100, 201, 176, 166, 42, 82, 67, 127, 245, 33, 126, 75, 138, 96, 3, 111, 17, 116, 224, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8