Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c5e6ce7308ee5f579f460641eececb12065addf8027d3b00f1a615e6c140817

Tx prefix hash: 2a71a0bb891b7d72d1d938c2e6cd76c2782086aa18aa9af0a1d3cac3a1085559
Tx public key: 840d309152367d6dc76fc5336bb21eaa057f296ff94b255e0f73dd40f2514dcb
Timestamp: 1732256906 Timestamp [UCT]: 2024-11-22 06:28:26 Age [y:d:h:m:s]: 00:002:00:13:39
Block: 1159073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1437 RingCT/type: yes/0
Extra: 01840d309152367d6dc76fc5336bb21eaa057f296ff94b255e0f73dd40f2514dcb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee798ba2930a4d6fca835a2c6f0bd34df041328239dc59f94404c55975bf05fb 0.600000000000 1644704 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": 1159083, "vin": [ { "gen": { "height": 1159073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee798ba2930a4d6fca835a2c6f0bd34df041328239dc59f94404c55975bf05fb" } } ], "extra": [ 1, 132, 13, 48, 145, 82, 54, 125, 109, 199, 111, 197, 51, 107, 178, 30, 170, 5, 127, 41, 111, 249, 75, 37, 94, 15, 115, 221, 64, 242, 81, 77, 203, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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