Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 592d5b8bf5a50501295cb31836e357d50762c597b1d92bce4b73401c64cca6ef

Tx prefix hash: 092d5ef8bbce236450672fa6fc8ff5f656a1bcbd6f8fb02e3ac947433c3d55e1
Tx public key: e22a4d406ecf28101e6e75e6d82d8869e44f7262c217cbaea13986ec50dc66b1
Timestamp: 1721715425 Timestamp [UCT]: 2024-07-23 06:17:05 Age [y:d:h:m:s]: 00:254:20:17:32
Block: 1071764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182053 RingCT/type: yes/0
Extra: 01e22a4d406ecf28101e6e75e6d82d8869e44f7262c217cbaea13986ec50dc66b102110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84a6d73e493dd340cef14a729ca00702e28f78fb632fa447d0421b0d915de175 0.600000000000 1544115 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": 1071774, "vin": [ { "gen": { "height": 1071764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84a6d73e493dd340cef14a729ca00702e28f78fb632fa447d0421b0d915de175" } } ], "extra": [ 1, 226, 42, 77, 64, 110, 207, 40, 16, 30, 110, 117, 230, 216, 45, 136, 105, 228, 79, 114, 98, 194, 23, 203, 174, 161, 57, 134, 236, 80, 220, 102, 177, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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