Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcfe924ebb7986486e9cd4ca55b2148e6d545f8f2d3916a59b21d885cd5b2621

Tx prefix hash: 4813c82465072c4e4c120a0d631ae518f6c2d892941c91c0982bcda3679e2fef
Tx public key: a9071897d7a6f2407de83d3b08d4023371c57879c744256b21ef82784c065911
Timestamp: 1673432219 Timestamp [UCT]: 2023-01-11 10:16:59 Age [y:d:h:m:s]: 02:086:20:50:51
Block: 672350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 583756 RingCT/type: yes/0
Extra: 01a9071897d7a6f2407de83d3b08d4023371c57879c744256b21ef82784c0659110211000000028b7b6602000000000000000000

1 output(s) for total of 3.632664569000 dcy

stealth address amount amount idx
00: 25df039b4b057fa3e0e1a555e1ec31c3f126a5b10e2a25c4d66d167f46035021 3.632664569000 1113879 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": 672360, "vin": [ { "gen": { "height": 672350 } } ], "vout": [ { "amount": 3632664569, "target": { "key": "25df039b4b057fa3e0e1a555e1ec31c3f126a5b10e2a25c4d66d167f46035021" } } ], "extra": [ 1, 169, 7, 24, 151, 215, 166, 242, 64, 125, 232, 61, 59, 8, 212, 2, 51, 113, 197, 120, 121, 199, 68, 37, 107, 33, 239, 130, 120, 76, 6, 89, 17, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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