Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0899c798fb5cc5ddc3f900224d8b6127f4323c5d89abb307b53b823a895806f5

Tx prefix hash: 4b699ffa9a1252e7e1c02d0df56b9606583e82050392995069aeceee71501de6
Tx public key: 76e956b3f3f82c140ede082f57bb22d42c9d00c4d74a5bf520783956d1772b39
Timestamp: 1727130538 Timestamp [UCT]: 2024-09-23 22:28:58 Age [y:d:h:m:s]: 00:122:14:22:33
Block: 1116677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87617 RingCT/type: yes/0
Extra: 0176e956b3f3f82c140ede082f57bb22d42c9d00c4d74a5bf520783956d1772b39021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12324a53c6b98433d4135e1ba51ae4faacb8ec588597a4b181d1211df8c5dbbc 0.600000000000 1597242 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": 1116687, "vin": [ { "gen": { "height": 1116677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12324a53c6b98433d4135e1ba51ae4faacb8ec588597a4b181d1211df8c5dbbc" } } ], "extra": [ 1, 118, 233, 86, 179, 243, 248, 44, 20, 14, 222, 8, 47, 87, 187, 34, 212, 44, 157, 0, 196, 215, 74, 91, 245, 32, 120, 57, 86, 209, 119, 43, 57, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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