Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f226668006eec2e7d2d03cb829cf460ec37fd9172569a1810f27c8eb4e330a35

Tx prefix hash: bf7a82ed49cc1493b9c4caff8e28bddf26ddd4e464cf8beca19998ee1f8d3adb
Tx public key: bc83ad1f036d0734292cc1d63021f49ce0617a20ecea05644bcd710a8583e9b5
Timestamp: 1726274617 Timestamp [UCT]: 2024-09-14 00:43:37 Age [y:d:h:m:s]: 01:056:23:32:07
Block: 1109576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299141 RingCT/type: yes/0
Extra: 01bc83ad1f036d0734292cc1d63021f49ce0617a20ecea05644bcd710a8583e9b502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bd935b74e8f3e997625f7e43ee4f2a1f60dc299c3f83557c22aa8ac4551203d 0.600000000000 1587875 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": 1109586, "vin": [ { "gen": { "height": 1109576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bd935b74e8f3e997625f7e43ee4f2a1f60dc299c3f83557c22aa8ac4551203d" } } ], "extra": [ 1, 188, 131, 173, 31, 3, 109, 7, 52, 41, 44, 193, 214, 48, 33, 244, 156, 224, 97, 122, 32, 236, 234, 5, 100, 75, 205, 113, 10, 133, 131, 233, 181, 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