Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf8d092e62725dcac71b69f3c1427fe5ca88eb1f7c40a870b33ba96cdddab6a6

Tx prefix hash: c052e5b7e23152c1b06bdcc0722792fcd2c8cdae86a71cb55f1fe10264ee06af
Tx public key: 319ca40ea85cc21a9119097353e0e715acbc8fbb778ab38f2f69dc9ac6d2b41f
Timestamp: 1719270858 Timestamp [UCT]: 2024-06-24 23:14:18 Age [y:d:h:m:s]: 00:291:20:10:39
Block: 1051496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208556 RingCT/type: yes/0
Extra: 01319ca40ea85cc21a9119097353e0e715acbc8fbb778ab38f2f69dc9ac6d2b41f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c81d61f0f148eac8ba0fe5bd7113793235bcf4393312b2cf1a75d5ba24ea9c0 0.600000000000 1521809 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": 1051506, "vin": [ { "gen": { "height": 1051496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c81d61f0f148eac8ba0fe5bd7113793235bcf4393312b2cf1a75d5ba24ea9c0" } } ], "extra": [ 1, 49, 156, 164, 14, 168, 92, 194, 26, 145, 25, 9, 115, 83, 224, 231, 21, 172, 188, 143, 187, 119, 138, 179, 143, 47, 105, 220, 154, 198, 210, 180, 31, 2, 17, 0, 0, 0, 2, 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