Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3cf913ab12b375b0ef9a660e180ca3636a2b628784569e5cc1e8fdd4e11cdf

Tx prefix hash: 1bccdb03d2cf4b7f8cb8cb57c868c1129df092fef112854ae6bbabbeacd17844
Tx public key: 230940a831b1c675fecdf38aa7d8552c906d0e3e297ac7f7dec451cce2a6cf2d
Timestamp: 1697443488 Timestamp [UCT]: 2023-10-16 08:04:48 Age [y:d:h:m:s]: 02:033:05:07:41
Block: 870748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543365 RingCT/type: yes/0
Extra: 01230940a831b1c675fecdf38aa7d8552c906d0e3e297ac7f7dec451cce2a6cf2d02110000000233af99f4000000000000000000

1 output(s) for total of 0.799568855000 dcy

stealth address amount amount idx
00: 4e86ac8d99f2c44eb72d7d88214b364ec6aa4367e4221fa7953f976f6c6a1a3c 0.799568855000 1325633 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": 870758, "vin": [ { "gen": { "height": 870748 } } ], "vout": [ { "amount": 799568855, "target": { "key": "4e86ac8d99f2c44eb72d7d88214b364ec6aa4367e4221fa7953f976f6c6a1a3c" } } ], "extra": [ 1, 35, 9, 64, 168, 49, 177, 198, 117, 254, 205, 243, 138, 167, 216, 85, 44, 144, 109, 14, 62, 41, 122, 199, 247, 222, 196, 81, 204, 226, 166, 207, 45, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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