Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd27cfa153319d49904d6c69bcf30e3c0b95f06f0354bdceedf97098bade1dfc

Tx prefix hash: 09576d5d19705f14edd95cb00fadb060ef4f9ec38ddafd22ff96aea722e1b4fc
Tx public key: ee254dfeb603c21b210981c59c41c39e4b6434ef19cbc0e29deeeaac30e0bb2f
Timestamp: 1705648103 Timestamp [UCT]: 2024-01-19 07:08:23 Age [y:d:h:m:s]: 01:116:20:41:25
Block: 938549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344643 RingCT/type: yes/0
Extra: 01ee254dfeb603c21b210981c59c41c39e4b6434ef19cbc0e29deeeaac30e0bb2f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d463d79a0b2363bd9796ba789b09a20ab38cc95b6db89dac5c6285f6ae9afb6 0.600000000000 1396619 of 15

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": 938559, "vin": [ { "gen": { "height": 938549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d463d79a0b2363bd9796ba789b09a20ab38cc95b6db89dac5c6285f6ae9afb6" } } ], "extra": [ 1, 238, 37, 77, 254, 182, 3, 194, 27, 33, 9, 129, 197, 156, 65, 195, 158, 75, 100, 52, 239, 25, 203, 192, 226, 157, 238, 234, 172, 48, 224, 187, 47, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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