Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c699fcd118f5d65c34ee669454b54bfe5579a3bc43b3571fb142388af44a8d09

Tx prefix hash: 846a6634039e53a73c812d72da6d25ca1e6704d365525b16befa1dbfde4b2759
Tx public key: ffdccf7a8861a82bba99513bb4c43f9cf585a67bf162580ec41fa29b9d0ca99a
Timestamp: 1735653450 Timestamp [UCT]: 2024-12-31 13:57:30 Age [y:d:h:m:s]: 00:090:08:19:17
Block: 1187196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64357 RingCT/type: yes/0
Extra: 01ffdccf7a8861a82bba99513bb4c43f9cf585a67bf162580ec41fa29b9d0ca99a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b72c6cb0ff6d075fcb2b0e08aa6c7facd8d532c0b4400e276320f1077129f6e 0.600000000000 1673683 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": 1187206, "vin": [ { "gen": { "height": 1187196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b72c6cb0ff6d075fcb2b0e08aa6c7facd8d532c0b4400e276320f1077129f6e" } } ], "extra": [ 1, 255, 220, 207, 122, 136, 97, 168, 43, 186, 153, 81, 59, 180, 196, 63, 156, 245, 133, 166, 123, 241, 98, 88, 14, 196, 31, 162, 155, 157, 12, 169, 154, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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