Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675ca14a50d2bed0b5cfc3dcc18f77f834f271b47e616e2551d5c9629d0d6504

Tx prefix hash: b1b11e3bbeb1a69404c0935a004b8a34e1bb0a2c2ea0c478603bd0e0b4d6e603
Tx public key: e0d2c4f60e63e21fbdd2fb702afccb688b62953ba5c7bc2c4a986b316098ddc1
Timestamp: 1705399757 Timestamp [UCT]: 2024-01-16 10:09:17 Age [y:d:h:m:s]: 00:360:11:08:46
Block: 936494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258081 RingCT/type: yes/0
Extra: 01e0d2c4f60e63e21fbdd2fb702afccb688b62953ba5c7bc2c4a986b316098ddc102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb0ea5794f93e18dea6d4a6b5550303ff8e2b242f76c62e9aedc578ba203e73 0.600000000000 1394522 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": 936504, "vin": [ { "gen": { "height": 936494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb0ea5794f93e18dea6d4a6b5550303ff8e2b242f76c62e9aedc578ba203e73" } } ], "extra": [ 1, 224, 210, 196, 246, 14, 99, 226, 31, 189, 210, 251, 112, 42, 252, 203, 104, 139, 98, 149, 59, 165, 199, 188, 44, 74, 152, 107, 49, 96, 152, 221, 193, 2, 17, 0, 0, 0, 4, 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