Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efdf4408885bd67fb00a0c546b18d5502a597e90b41c106ff099b39269633bab

Tx prefix hash: f20f64cd82ac0f3e7384dceed23d2253a8a7e18a6bbe7aea528762ad7bba7c9a
Tx public key: dd0d95a317ad813deacbaf94e2840cb9f475d2a0ad2a02a41d6d59ffe6f53e63
Timestamp: 1639256608 Timestamp [UCT]: 2021-12-11 21:03:28 Age [y:d:h:m:s]: 02:329:07:50:13
Block: 393437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753417 RingCT/type: yes/0
Extra: 01dd0d95a317ad813deacbaf94e2840cb9f475d2a0ad2a02a41d6d59ffe6f53e63021100000001408d5ef5000000000000000000

1 output(s) for total of 30.505648132000 dcy

stealth address amount amount idx
00: dad911fb623ea7edaeff7e0b5a8ff81a28f1320e6204f15cd086e3b4bcbec3ed 30.505648132000 790668 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": 393447, "vin": [ { "gen": { "height": 393437 } } ], "vout": [ { "amount": 30505648132, "target": { "key": "dad911fb623ea7edaeff7e0b5a8ff81a28f1320e6204f15cd086e3b4bcbec3ed" } } ], "extra": [ 1, 221, 13, 149, 163, 23, 173, 129, 61, 234, 203, 175, 148, 226, 132, 12, 185, 244, 117, 210, 160, 173, 42, 2, 164, 29, 109, 89, 255, 230, 245, 62, 99, 2, 17, 0, 0, 0, 1, 64, 141, 94, 245, 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