Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f93620f6c44de9269a50e6b1efcc04a79265930519bff224cd38cf9f676a3bb9

Tx prefix hash: f5c3f87d49bbde4650582f364f08a3633a71044b7d6f2e85be696c0d8de0eb33
Tx public key: b281b510ec2bc4de99fa8c7e2734703d0d49570ffc7922a4f6ade69303d6acc4
Timestamp: 1715191204 Timestamp [UCT]: 2024-05-08 18:00:04 Age [y:d:h:m:s]: 00:135:13:55:40
Block: 1017702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97102 RingCT/type: yes/0
Extra: 01b281b510ec2bc4de99fa8c7e2734703d0d49570ffc7922a4f6ade69303d6acc40211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0c1bb76358b54458c402a54efab129338b0e7ec45da35242ebc33f4d6d0c3a6 0.600000000000 1481487 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": 1017712, "vin": [ { "gen": { "height": 1017702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0c1bb76358b54458c402a54efab129338b0e7ec45da35242ebc33f4d6d0c3a6" } } ], "extra": [ 1, 178, 129, 181, 16, 236, 43, 196, 222, 153, 250, 140, 126, 39, 52, 112, 61, 13, 73, 87, 15, 252, 121, 34, 164, 246, 173, 230, 147, 3, 214, 172, 196, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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