Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9c2d11f7080628c78d0af1017bef0b3cf1132e6c3a80410736107a0a169062

Tx prefix hash: debcfd390a23eb215b251d275073ecba7b96846ee8f7a13da127a6cfec6e52d4
Tx public key: f1e09d6c211a24740ebf4ba4141f6c4d4a69e1c81744212f8daa54d93ae4c415
Timestamp: 1638781040 Timestamp [UCT]: 2021-12-06 08:57:20 Age [y:d:h:m:s]: 03:330:04:58:10
Block: 389556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1012420 RingCT/type: yes/0
Extra: 01f1e09d6c211a24740ebf4ba4141f6c4d4a69e1c81744212f8daa54d93ae4c415021100000013d6e4826b000000000000000000

1 output(s) for total of 31.422419792000 dcy

stealth address amount amount idx
00: de6d3db10ac4c2d382aee9d60892779c9958360dfec64282023ae45bb4e9407c 31.422419792000 784767 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": 389566, "vin": [ { "gen": { "height": 389556 } } ], "vout": [ { "amount": 31422419792, "target": { "key": "de6d3db10ac4c2d382aee9d60892779c9958360dfec64282023ae45bb4e9407c" } } ], "extra": [ 1, 241, 224, 157, 108, 33, 26, 36, 116, 14, 191, 75, 164, 20, 31, 108, 77, 74, 105, 225, 200, 23, 68, 33, 47, 141, 170, 84, 217, 58, 228, 196, 21, 2, 17, 0, 0, 0, 19, 214, 228, 130, 107, 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