Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc066c084921ece8bc6154908a38eab1625e217e4a010e3ad6cbc19000b345df

Tx prefix hash: 8c14abb71735fcd382f4db7c76b661444802a416f32bfd443e244727632530a9
Tx public key: e7e4427891b7e5d78229f575d9bf96b83f32f6af645f15ec79452022b4c1e324
Timestamp: 1722639402 Timestamp [UCT]: 2024-08-02 22:56:42 Age [y:d:h:m:s]: 00:246:08:41:07
Block: 1079430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175982 RingCT/type: yes/0
Extra: 01e7e4427891b7e5d78229f575d9bf96b83f32f6af645f15ec79452022b4c1e32402110000000be914dd15000000000000000000

1 output(s) for total of 0.607780000000 dcy

stealth address amount amount idx
00: 0b5186de9179145b1aa056a2fb208a7ff4fd2cdea986386e020d9d8fffa31dfc 0.607780000000 1552381 of 0

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": 1079440, "vin": [ { "gen": { "height": 1079430 } } ], "vout": [ { "amount": 607780000, "target": { "key": "0b5186de9179145b1aa056a2fb208a7ff4fd2cdea986386e020d9d8fffa31dfc" } } ], "extra": [ 1, 231, 228, 66, 120, 145, 183, 229, 215, 130, 41, 245, 117, 217, 191, 150, 184, 63, 50, 246, 175, 100, 95, 21, 236, 121, 69, 32, 34, 180, 193, 227, 36, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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