Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597cc78d556c31744bc85fd3e59908dbd214ffd4af960ae171506501d997bd39

Tx prefix hash: 3549c4a8d9f41f2b9cda24704143ea158e91485f9038a9eb4bd094833ee208b7
Tx public key: 492e0370f9d9f28403f4704f27f2d6910f00fedd3a21d465f41ad26302ffc3cf
Timestamp: 1695000767 Timestamp [UCT]: 2023-09-18 01:32:47 Age [y:d:h:m:s]: 01:122:22:08:16
Block: 850480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349168 RingCT/type: yes/0
Extra: 01492e0370f9d9f28403f4704f27f2d6910f00fedd3a21d465f41ad26302ffc3cf021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.933268838000 dcy

stealth address amount amount idx
00: 528f0e754ed89daa697e686a6c2cfc5edd3910f259bd1707ccdf60632f7e9d9a 0.933268838000 1304200 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": 850490, "vin": [ { "gen": { "height": 850480 } } ], "vout": [ { "amount": 933268838, "target": { "key": "528f0e754ed89daa697e686a6c2cfc5edd3910f259bd1707ccdf60632f7e9d9a" } } ], "extra": [ 1, 73, 46, 3, 112, 249, 217, 242, 132, 3, 244, 112, 79, 39, 242, 214, 145, 15, 0, 254, 221, 58, 33, 212, 101, 244, 26, 210, 99, 2, 255, 195, 207, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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