Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33283af9de20087dcd74029408ae7b0c22597678a0b0df4bb147148e68b71fed

Tx prefix hash: 88b3f6edb041d2f43dca78206eab7614876ed45a74884c56c30097550e70076b
Tx public key: 6727d4d4b65ce06b2662ca2e0b5cd0a44493a7d28a0baa045d3f5cae25cd39db
Timestamp: 1702550936 Timestamp [UCT]: 2023-12-14 10:48:56 Age [y:d:h:m:s]: 01:118:16:55:13
Block: 912886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345986 RingCT/type: yes/0
Extra: 016727d4d4b65ce06b2662ca2e0b5cd0a44493a7d28a0baa045d3f5cae25cd39db021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a7305fb5ece8aa49ce6445f0fe005bcfd0b3650dc6ab59a236c29d3ca479c26 0.600000000000 1370122 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": 912896, "vin": [ { "gen": { "height": 912886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a7305fb5ece8aa49ce6445f0fe005bcfd0b3650dc6ab59a236c29d3ca479c26" } } ], "extra": [ 1, 103, 39, 212, 212, 182, 92, 224, 107, 38, 98, 202, 46, 11, 92, 208, 164, 68, 147, 167, 210, 138, 11, 170, 4, 93, 63, 92, 174, 37, 205, 57, 219, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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