Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4853860ec8ba8e7a012bccd72bbbb814967e933f7d9f35cf8360ecbd5523efed

Tx prefix hash: e01e37f7d361d79f51ede6bca186412e07ecd9143e0bcd9d59b20f035e3396a0
Tx public key: 2df8c1cb45e6af008836b95a70ea7e82743ba9101bbf3445b0952d829283f7be
Timestamp: 1725408979 Timestamp [UCT]: 2024-09-04 00:16:19 Age [y:d:h:m:s]: 00:238:22:33:57
Block: 1102404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170624 RingCT/type: yes/0
Extra: 012df8c1cb45e6af008836b95a70ea7e82743ba9101bbf3445b0952d829283f7be02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71200840e940fba87007608692a39bd75fb7179f2fd3c64adb302be214efa8fe 0.600000000000 1578827 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": 1102414, "vin": [ { "gen": { "height": 1102404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71200840e940fba87007608692a39bd75fb7179f2fd3c64adb302be214efa8fe" } } ], "extra": [ 1, 45, 248, 193, 203, 69, 230, 175, 0, 136, 54, 185, 90, 112, 234, 126, 130, 116, 59, 169, 16, 27, 191, 52, 69, 176, 149, 45, 130, 146, 131, 247, 190, 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