Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e97577ba8cac214eeb353f466567fcbbb20ab922d38327ab3f7aa2f198485f9

Tx prefix hash: c5c372d6420f0d0dd2d6636614bec81738cb7c68491f33701f51b22d52ebd172
Tx public key: e96d13bd76c2c70d7728fc5d51a9c07999e4bfcd90eca829a416dbe7feb6afe8
Timestamp: 1749552757 Timestamp [UCT]: 2025-06-10 10:52:37 Age [y:d:h:m:s]: 00:163:08:29:53
Block: 1302009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114432 RingCT/type: yes/0
Extra: 01e96d13bd76c2c70d7728fc5d51a9c07999e4bfcd90eca829a416dbe7feb6afe8021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc4a8a8b6fbdc16a7b98ce498d6dc26cfd6ea856c34d520cc09c7e9c8046020b 0.600000000000 1789578 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": 1302019, "vin": [ { "gen": { "height": 1302009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc4a8a8b6fbdc16a7b98ce498d6dc26cfd6ea856c34d520cc09c7e9c8046020b" } } ], "extra": [ 1, 233, 109, 19, 189, 118, 194, 199, 13, 119, 40, 252, 93, 81, 169, 192, 121, 153, 228, 191, 205, 144, 236, 168, 41, 164, 22, 219, 231, 254, 182, 175, 232, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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