Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17cd902b4fcb63a1058704babb7e770e3315075a8fdd9b40b5424f2ba3c47e3

Tx prefix hash: acb4420e051a6547a12353099fe81aaac34b5cb12fa6d24b305858ca875dbd63
Tx public key: fa4446b8a18b3a9f73823b442c66f661f9f2594904d3d799ba29d315150b3250
Timestamp: 1699857306 Timestamp [UCT]: 2023-11-13 06:35:06 Age [y:d:h:m:s]: 01:167:14:57:08
Block: 890564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381008 RingCT/type: yes/0
Extra: 01fa4446b8a18b3a9f73823b442c66f661f9f2594904d3d799ba29d315150b3250021100000001faf35c9c000000000000000000

1 output(s) for total of 0.687371901000 dcy

stealth address amount amount idx
00: d3a69ba75e2ffdc31c1b4268e72970a5a662ddf092114ae3cc12e618c99e56af 0.687371901000 1346587 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": 890574, "vin": [ { "gen": { "height": 890564 } } ], "vout": [ { "amount": 687371901, "target": { "key": "d3a69ba75e2ffdc31c1b4268e72970a5a662ddf092114ae3cc12e618c99e56af" } } ], "extra": [ 1, 250, 68, 70, 184, 161, 139, 58, 159, 115, 130, 59, 68, 44, 102, 246, 97, 249, 242, 89, 73, 4, 211, 215, 153, 186, 41, 211, 21, 21, 11, 50, 80, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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