Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990ca187cc886ffa04bb4fd1a4a14bbf8019bb754d352a343228c8f418036cfa

Tx prefix hash: 79df4de89d7a8c3cf8186c8066e93a1723d6a93365da6004308b6bb2eff2b862
Tx public key: 068c717658ddf1288f051a12c1e743df419eba3bc724007f18acb0be69c3f08e
Timestamp: 1725119490 Timestamp [UCT]: 2024-08-31 15:51:30 Age [y:d:h:m:s]: 00:213:15:26:37
Block: 1099990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152540 RingCT/type: yes/0
Extra: 01068c717658ddf1288f051a12c1e743df419eba3bc724007f18acb0be69c3f08e02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a314f8eb2df2a643bb67362ddfba4692adc02abd64b20d25b48a43522d6030 0.600000000000 1575961 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": 1100000, "vin": [ { "gen": { "height": 1099990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a314f8eb2df2a643bb67362ddfba4692adc02abd64b20d25b48a43522d6030" } } ], "extra": [ 1, 6, 140, 113, 118, 88, 221, 241, 40, 143, 5, 26, 18, 193, 231, 67, 223, 65, 158, 186, 59, 199, 36, 0, 127, 24, 172, 176, 190, 105, 195, 240, 142, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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