Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86452bc084df0b15bd750d37bf8157484b207768275ccab8f1104f95037199c9

Tx prefix hash: 1a6387943768b2d8c9d1aec056fe560f174f266bed5c192d2313ce63197a0122
Tx public key: ff3002408d5f936ba5b7e6ed6e1b8f8278617798a6b2aa3daea32bc01429f7ce
Timestamp: 1702566919 Timestamp [UCT]: 2023-12-14 15:15:19 Age [y:d:h:m:s]: 00:282:07:20:13
Block: 913023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202225 RingCT/type: yes/0
Extra: 01ff3002408d5f936ba5b7e6ed6e1b8f8278617798a6b2aa3daea32bc01429f7ce02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d1bba4fb02981786040ef7c0c9f22b63f56eded3e70ce1c947a21c22b200f00 0.600000000000 1370263 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": 913033, "vin": [ { "gen": { "height": 913023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d1bba4fb02981786040ef7c0c9f22b63f56eded3e70ce1c947a21c22b200f00" } } ], "extra": [ 1, 255, 48, 2, 64, 141, 95, 147, 107, 165, 183, 230, 237, 110, 27, 143, 130, 120, 97, 119, 152, 166, 178, 170, 61, 174, 163, 43, 192, 20, 41, 247, 206, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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