Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81253dd473bcd2c2f7b1f92b56bc58255836522177a0973e9db63c23fb0ef068

Tx prefix hash: a0c44a74c5a3fda2f8b82c549bc6cf5664c5cdc14bdb97e737ac2da3a7ea9275
Tx public key: d39d1ce3f81548c95ff07b56eb7a240a9fd5eec0284a55692e3930829c05b99a
Timestamp: 1713998356 Timestamp [UCT]: 2024-04-24 22:39:16 Age [y:d:h:m:s]: 01:052:09:13:38
Block: 1007799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298306 RingCT/type: yes/0
Extra: 01d39d1ce3f81548c95ff07b56eb7a240a9fd5eec0284a55692e3930829c05b99a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ba83436830517efc9526848111eb91a83ea04f47ee3eeb065b4d3ca1245d53 0.600000000000 1469253 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": 1007809, "vin": [ { "gen": { "height": 1007799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ba83436830517efc9526848111eb91a83ea04f47ee3eeb065b4d3ca1245d53" } } ], "extra": [ 1, 211, 157, 28, 227, 248, 21, 72, 201, 95, 240, 123, 86, 235, 122, 36, 10, 159, 213, 238, 192, 40, 74, 85, 105, 46, 57, 48, 130, 156, 5, 185, 154, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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