Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29363ef55476fb9de39825a872cfba5deedfd3d1a3062dbd57edcc0c7f1a3b90

Tx prefix hash: 27231706285d1046b717941fd7f64f73dd5d4c9a931208fb0949782291bc3917
Tx public key: 3b2dd7e8b1ec3ae97ce05b930f37d56584dfe8f4d1f1aa2e64c994409a877fb4
Timestamp: 1675418892 Timestamp [UCT]: 2023-02-03 10:08:12 Age [y:d:h:m:s]: 01:328:04:25:39
Block: 688831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495527 RingCT/type: yes/0
Extra: 013b2dd7e8b1ec3ae97ce05b930f37d56584dfe8f4d1f1aa2e64c994409a877fb4021100000001e7ace25d000000000000000000

1 output(s) for total of 3.203442103000 dcy

stealth address amount amount idx
00: 9f4b1009aac0a6daa0514fad69c204aec9e679aac7ae6d464afd662180163c4f 3.203442103000 1131477 of 0

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": 688841, "vin": [ { "gen": { "height": 688831 } } ], "vout": [ { "amount": 3203442103, "target": { "key": "9f4b1009aac0a6daa0514fad69c204aec9e679aac7ae6d464afd662180163c4f" } } ], "extra": [ 1, 59, 45, 215, 232, 177, 236, 58, 233, 124, 224, 91, 147, 15, 55, 213, 101, 132, 223, 232, 244, 209, 241, 170, 46, 100, 201, 148, 64, 154, 135, 127, 180, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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