Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb57ef6831836b9bcb55d623ea2197526770dc7c35d5bea47a508605108d277

Tx prefix hash: 70577e7de8d3b9128cb6f580d051c1d63e7691db828980d3b8bf325a98728b3c
Tx public key: be8fe61bb6bf22550612c6470b87b029e859e0f4af58d03c0a52ecd0fb312ebc
Timestamp: 1705078404 Timestamp [UCT]: 2024-01-12 16:53:24 Age [y:d:h:m:s]: 01:087:10:02:36
Block: 933828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323580 RingCT/type: yes/0
Extra: 01be8fe61bb6bf22550612c6470b87b029e859e0f4af58d03c0a52ecd0fb312ebc02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42567ffc6ca8174985d4fb0601c0a32dde9e89fe3bf46af527ce1d3288664736 0.600000000000 1391810 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": 933838, "vin": [ { "gen": { "height": 933828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42567ffc6ca8174985d4fb0601c0a32dde9e89fe3bf46af527ce1d3288664736" } } ], "extra": [ 1, 190, 143, 230, 27, 182, 191, 34, 85, 6, 18, 198, 71, 11, 135, 176, 41, 232, 89, 224, 244, 175, 88, 208, 60, 10, 82, 236, 208, 251, 49, 46, 188, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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