Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f1557bc75015d61b991d12e10d690187abc99ef699c155d4ee380e2e0fad24

Tx prefix hash: b3c1f864055adc7e4287f5a50e9f71a47438bef5be418920829264a6ca15ab7c
Tx public key: cced0d86cba8199de630a5597dc1f0e55d44c7f058eed10c786131a4e27c9571
Timestamp: 1712957129 Timestamp [UCT]: 2024-04-12 21:25:29 Age [y:d:h:m:s]: 01:003:23:17:12
Block: 999144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263807 RingCT/type: yes/0
Extra: 01cced0d86cba8199de630a5597dc1f0e55d44c7f058eed10c786131a4e27c957102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eaf4fcc016edfb5f7e36c451cf78b3d3ff8ba87222aacea6c5157dedcbbdf5c 0.600000000000 1459622 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": 999154, "vin": [ { "gen": { "height": 999144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eaf4fcc016edfb5f7e36c451cf78b3d3ff8ba87222aacea6c5157dedcbbdf5c" } } ], "extra": [ 1, 204, 237, 13, 134, 203, 168, 25, 157, 230, 48, 165, 89, 125, 193, 240, 229, 93, 68, 199, 240, 88, 238, 209, 12, 120, 97, 49, 164, 226, 124, 149, 113, 2, 17, 0, 0, 0, 2, 89, 218, 211, 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