Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2357ccabb6bd3960759bde767d6b34c9e3fd3a29035e962802ae32932cf0d361

Tx prefix hash: c489dac2cdd111a347eebda1e39c4eafc67a68fad902357cc9f43f95a30e818b
Tx public key: 2f5544c5015cec2d760dfebca84426c87502a82af1bb32e0a4a2c5b6ad5db360
Timestamp: 1712922951 Timestamp [UCT]: 2024-04-12 11:55:51 Age [y:d:h:m:s]: 01:201:22:05:04
Block: 998866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402997 RingCT/type: yes/0
Extra: 012f5544c5015cec2d760dfebca84426c87502a82af1bb32e0a4a2c5b6ad5db36002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8deb39617f4e305b240a37ce9117795da9fd2a3bf41a83e3db070a6199af06a1 0.600000000000 1459332 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": 998876, "vin": [ { "gen": { "height": 998866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8deb39617f4e305b240a37ce9117795da9fd2a3bf41a83e3db070a6199af06a1" } } ], "extra": [ 1, 47, 85, 68, 197, 1, 92, 236, 45, 118, 13, 254, 188, 168, 68, 38, 200, 117, 2, 168, 42, 241, 187, 50, 224, 164, 162, 197, 182, 173, 93, 179, 96, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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