Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce9eb499c0409e4b5ab6949ee4e75e2027734495ff722712b8b564fda54f9b4f

Tx prefix hash: 61e56ce3625470a3971001358561f72f5e3a928242d28b1379f763f402a0fb96
Tx public key: f667f3ed0c825fd730484e77fcaeaf304c458c5fc92d1dca0cb45cd7bc891446
Timestamp: 1705316300 Timestamp [UCT]: 2024-01-15 10:58:20 Age [y:d:h:m:s]: 01:042:13:07:01
Block: 935808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291467 RingCT/type: yes/0
Extra: 01f667f3ed0c825fd730484e77fcaeaf304c458c5fc92d1dca0cb45cd7bc89144602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bcbd61d284487a4ba839a1b4af6ec14b590cdb9787427c923c691f229fa334d 0.600000000000 1393826 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": 935818, "vin": [ { "gen": { "height": 935808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bcbd61d284487a4ba839a1b4af6ec14b590cdb9787427c923c691f229fa334d" } } ], "extra": [ 1, 246, 103, 243, 237, 12, 130, 95, 215, 48, 72, 78, 119, 252, 174, 175, 48, 76, 69, 140, 95, 201, 45, 29, 202, 12, 180, 92, 215, 188, 137, 20, 70, 2, 17, 0, 0, 0, 5, 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