Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 756cba6b6d16986282db8e43b96be6b25601ddbb2a8eb8f581058b44de34262b

Tx prefix hash: 6d05b9e22339b1104ab552c5992d2d5d017a6d2c1c9b0812bd4daedabd61a032
Tx public key: 5b0a36a7ceaaca34429d3e7f3412cc94e135c4c667e350574faae4ee292af896
Timestamp: 1724208421 Timestamp [UCT]: 2024-08-21 02:47:01 Age [y:d:h:m:s]: 00:154:19:07:00
Block: 1092452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110673 RingCT/type: yes/0
Extra: 015b0a36a7ceaaca34429d3e7f3412cc94e135c4c667e350574faae4ee292af89602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4c8337675305a28e034ca0ca5f6b563a7089126a5b4d85fc223fb59e0c6baa7 0.600000000000 1567201 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": 1092462, "vin": [ { "gen": { "height": 1092452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4c8337675305a28e034ca0ca5f6b563a7089126a5b4d85fc223fb59e0c6baa7" } } ], "extra": [ 1, 91, 10, 54, 167, 206, 170, 202, 52, 66, 157, 62, 127, 52, 18, 204, 148, 225, 53, 196, 198, 103, 227, 80, 87, 79, 170, 228, 238, 41, 42, 248, 150, 2, 17, 0, 0, 0, 5, 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