Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c205fd3e530efb15bfec2b36917dcbe56989a21df7d86ff724af3494083a7a1

Tx prefix hash: 535b7922f48c10b041f01f3debd09cce47d13e6532c150795afd76dd56498005
Tx public key: f36bca171b99a08718ebd1eef8fe98b111c9601523b18cd2e211b3584cf730b6
Timestamp: 1715351866 Timestamp [UCT]: 2024-05-10 14:37:46 Age [y:d:h:m:s]: 00:257:05:24:03
Block: 1019022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184060 RingCT/type: yes/0
Extra: 01f36bca171b99a08718ebd1eef8fe98b111c9601523b18cd2e211b3584cf730b602110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86bbc7a4ce0ce064dfcd5d03739c1160c7b8fd729b83a40a3dcb76f05e7732c9 0.600000000000 1482879 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": 1019032, "vin": [ { "gen": { "height": 1019022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86bbc7a4ce0ce064dfcd5d03739c1160c7b8fd729b83a40a3dcb76f05e7732c9" } } ], "extra": [ 1, 243, 107, 202, 23, 27, 153, 160, 135, 24, 235, 209, 238, 248, 254, 152, 177, 17, 201, 96, 21, 35, 177, 140, 210, 226, 17, 179, 88, 76, 247, 48, 182, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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