Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4b5f5a70f64d8e5c04c54115f3f4eff08967caa4f4fa0f3a88015e0d064bc81

Tx prefix hash: 52855a02540f50c1ae6b1f265914efb7859fe7f40aa25c7460e94924ad4fc8e9
Tx public key: b7336c9e801b92ad196bb0748895e2710d41744d2bc5670a81d90aaccf8fd2d4
Timestamp: 1711799049 Timestamp [UCT]: 2024-03-30 11:44:09 Age [y:d:h:m:s]: 01:068:21:01:16
Block: 989587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310213 RingCT/type: yes/0
Extra: 01b7336c9e801b92ad196bb0748895e2710d41744d2bc5670a81d90aaccf8fd2d40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d602fa8c2a1b90e3a2354d562862131bc0a8b058e29ba5eae9cf8901bc12862f 0.600000000000 1449886 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": 989597, "vin": [ { "gen": { "height": 989587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d602fa8c2a1b90e3a2354d562862131bc0a8b058e29ba5eae9cf8901bc12862f" } } ], "extra": [ 1, 183, 51, 108, 158, 128, 27, 146, 173, 25, 107, 176, 116, 136, 149, 226, 113, 13, 65, 116, 77, 43, 197, 103, 10, 129, 217, 10, 172, 207, 143, 210, 212, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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