Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad92a15017ad8ebcf473edb2946c0f1351a87623ec96336dea33222faed64b27

Tx prefix hash: 2a3b76bb2d72a62ab11a098766c0aa506e44866480eb89f5d36310d85b68599e
Tx public key: 9f3f4743fd0578a131c8fd6c7154107bf5038057b850e03e1f1e442fe0a9b673
Timestamp: 1583079951 Timestamp [UCT]: 2020-03-01 16:25:51 Age [y:d:h:m:s]: 04:259:11:28:25
Block: 74589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1079392 RingCT/type: yes/0
Extra: 019f3f4743fd0578a131c8fd6c7154107bf5038057b850e03e1f1e442fe0a9b673021100000191026b59f3000000000000000000

1 output(s) for total of 347.421329187000 dcy

stealth address amount amount idx
00: 3950936b88fe1ddef9becbdf54d6a149c97b20124d75bf3ead33756a3258ae5e 347.421329187000 138007 of 0

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": 74599, "vin": [ { "gen": { "height": 74589 } } ], "vout": [ { "amount": 347421329187, "target": { "key": "3950936b88fe1ddef9becbdf54d6a149c97b20124d75bf3ead33756a3258ae5e" } } ], "extra": [ 1, 159, 63, 71, 67, 253, 5, 120, 161, 49, 200, 253, 108, 113, 84, 16, 123, 245, 3, 128, 87, 184, 80, 224, 62, 31, 30, 68, 47, 224, 169, 182, 115, 2, 17, 0, 0, 1, 145, 2, 107, 89, 243, 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