Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e58e57befe553fe9b685d9b5dad725fa057683c8ea3a81c6bd65ffef64f89b1d

Tx prefix hash: 1bb80906653f2500961bea3d6c56cc6387258ba740e730fe47cad1529a7e90d3
Tx public key: dfdeb64ea7c1ba5008932a900c088abee19d0d789e280b502f39a429c6bebdc5
Timestamp: 1726541661 Timestamp [UCT]: 2024-09-17 02:54:21 Age [y:d:h:m:s]: 00:068:11:17:50
Block: 1111788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48950 RingCT/type: yes/0
Extra: 01dfdeb64ea7c1ba5008932a900c088abee19d0d789e280b502f39a429c6bebdc502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fb1f3e493f00432ea856afabd0488abc5b621d5eb17ceb0bf20b0a76bb197d1 0.600000000000 1590869 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": 1111798, "vin": [ { "gen": { "height": 1111788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fb1f3e493f00432ea856afabd0488abc5b621d5eb17ceb0bf20b0a76bb197d1" } } ], "extra": [ 1, 223, 222, 182, 78, 167, 193, 186, 80, 8, 147, 42, 144, 12, 8, 138, 190, 225, 157, 13, 120, 158, 40, 11, 80, 47, 57, 164, 41, 198, 190, 189, 197, 2, 17, 0, 0, 0, 2, 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