Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d95b27984e97c26733c0900ed182eea14005576cfc3c4b136974224243e9a49

Tx prefix hash: 3639fafe9d5cdebd826f038248e96f23561e96b06a60449f29d7fa4d87717e54
Tx public key: 59afaca1a1ecc9df540ad963f20fedca187f58d26489e598cd8c3f96ae25df0b
Timestamp: 1687751546 Timestamp [UCT]: 2023-06-26 03:52:26 Age [y:d:h:m:s]: 01:293:12:28:22
Block: 790464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470929 RingCT/type: yes/0
Extra: 0159afaca1a1ecc9df540ad963f20fedca187f58d26489e598cd8c3f96ae25df0b0211000000044b8f5122000000000000000000

1 output(s) for total of 1.475247117000 dcy

stealth address amount amount idx
00: b5773a1c9e9592a1c5987aa80887b39e796744f09ced34256bf742042fb9e1e9 1.475247117000 1240809 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": 790474, "vin": [ { "gen": { "height": 790464 } } ], "vout": [ { "amount": 1475247117, "target": { "key": "b5773a1c9e9592a1c5987aa80887b39e796744f09ced34256bf742042fb9e1e9" } } ], "extra": [ 1, 89, 175, 172, 161, 161, 236, 201, 223, 84, 10, 217, 99, 242, 15, 237, 202, 24, 127, 88, 210, 100, 137, 229, 152, 205, 140, 63, 150, 174, 37, 223, 11, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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