Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a123109f591d3f4512679631124a1a3ba0759805f056ea1bc4681603a7d35d1

Tx prefix hash: 6acb1bbc2f303a59236114355cefe750562d05f173370e636903a8a20267893d
Tx public key: ca57cbf28315b374ca5cbf10b6dda380b4dbf5e685efb8e3ed903491d46efa6e
Timestamp: 1682855391 Timestamp [UCT]: 2023-04-30 11:49:51 Age [y:d:h:m:s]: 01:302:11:24:43
Block: 749855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477399 RingCT/type: yes/0
Extra: 01ca57cbf28315b374ca5cbf10b6dda380b4dbf5e685efb8e3ed903491d46efa6e021100000003b3164c24000000000000000000

1 output(s) for total of 2.011033516000 dcy

stealth address amount amount idx
00: 7f85f7d758f59cdc3c5e591b14bc0d7e08ab5c9d6c89b75ba1c4039199dff14a 2.011033516000 1197872 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": 749865, "vin": [ { "gen": { "height": 749855 } } ], "vout": [ { "amount": 2011033516, "target": { "key": "7f85f7d758f59cdc3c5e591b14bc0d7e08ab5c9d6c89b75ba1c4039199dff14a" } } ], "extra": [ 1, 202, 87, 203, 242, 131, 21, 179, 116, 202, 92, 191, 16, 182, 221, 163, 128, 180, 219, 245, 230, 133, 239, 184, 227, 237, 144, 52, 145, 212, 110, 250, 110, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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