Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c7cf2ef084f6377ed12a62f8538b914be3dc69db947fc736ac7618a8cfcb82

Tx prefix hash: 2da39c3f59ff46d57c96bc2546c3fe2eade9197bd95c09ee2b5d41c3a1385ac8
Tx public key: cf2e51d34754922f9f78068b1d94cab54d64534b889dd889004403f1c661d4dc
Timestamp: 1702914828 Timestamp [UCT]: 2023-12-18 15:53:48 Age [y:d:h:m:s]: 01:071:12:45:43
Block: 915908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312217 RingCT/type: yes/0
Extra: 01cf2e51d34754922f9f78068b1d94cab54d64534b889dd889004403f1c661d4dc02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d08edf16637f1c3e85c211f3dd9087ad54ceddbde1b4e6450a6a0d7c411a91e 0.600000000000 1373342 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": 915918, "vin": [ { "gen": { "height": 915908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d08edf16637f1c3e85c211f3dd9087ad54ceddbde1b4e6450a6a0d7c411a91e" } } ], "extra": [ 1, 207, 46, 81, 211, 71, 84, 146, 47, 159, 120, 6, 139, 29, 148, 202, 181, 77, 100, 83, 75, 136, 157, 216, 137, 0, 68, 3, 241, 198, 97, 212, 220, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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