Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b69246d8d19f1cc42a76431a7e1862a1b6576706301894d608308f9236b21a83

Tx prefix hash: be938f57393456bbf87f265b47c5c4c71d1d7db102f346f3b2080c2a50547b3a
Tx public key: f4a94e1d0fc8584988685a1997051d0df87b10dcb356a62d34d1ce59c2c301bc
Timestamp: 1714720146 Timestamp [UCT]: 2024-05-03 07:09:06 Age [y:d:h:m:s]: 00:264:15:53:29
Block: 1013798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189367 RingCT/type: yes/0
Extra: 01f4a94e1d0fc8584988685a1997051d0df87b10dcb356a62d34d1ce59c2c301bc0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d205670fee04f9e5d02bbfb15e8e974c96ad1eb7053eac094144496b6985d80e 0.600000000000 1476709 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": 1013808, "vin": [ { "gen": { "height": 1013798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d205670fee04f9e5d02bbfb15e8e974c96ad1eb7053eac094144496b6985d80e" } } ], "extra": [ 1, 244, 169, 78, 29, 15, 200, 88, 73, 136, 104, 90, 25, 151, 5, 29, 13, 248, 123, 16, 220, 179, 86, 166, 45, 52, 209, 206, 89, 194, 195, 1, 188, 2, 17, 0, 0, 0, 8, 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