Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 946ebe82dfc216a6cd4385aca51ec3c8b3b17e11c00fc93a96f104c6901c5e9e

Tx prefix hash: 2b250c14d35d92f6a993bac29e5a2582254b44bfea15734a745e4e300e2fd704
Tx public key: 338fdc69a1e89cea26bf70123e8ecd3fcccedcffed69b4b212971b22527c5b49
Timestamp: 1724419030 Timestamp [UCT]: 2024-08-23 13:17:10 Age [y:d:h:m:s]: 00:291:02:35:26
Block: 1094210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207951 RingCT/type: yes/0
Extra: 01338fdc69a1e89cea26bf70123e8ecd3fcccedcffed69b4b212971b22527c5b49021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1bad6c6c4b3b60f9cbf6a1818c9623af9f5cd3184a79b06d596454aab2566b7 0.600000000000 1569311 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": 1094220, "vin": [ { "gen": { "height": 1094210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1bad6c6c4b3b60f9cbf6a1818c9623af9f5cd3184a79b06d596454aab2566b7" } } ], "extra": [ 1, 51, 143, 220, 105, 161, 232, 156, 234, 38, 191, 112, 18, 62, 142, 205, 63, 204, 206, 220, 255, 237, 105, 180, 178, 18, 151, 27, 34, 82, 124, 91, 73, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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