Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24b2677e923470617681e7f74043d131d54e547e09f6c9991f0609fc1c191bf

Tx prefix hash: e949c04501772747e59cce8b91c1a1615a2968c02b0b5d7776cd047a699a6c33
Tx public key: 286cac720035f8c3f0ff64a14d9c5293af7f395c866096151d67a90a3daa3b72
Timestamp: 1699107889 Timestamp [UCT]: 2023-11-04 14:24:49 Age [y:d:h:m:s]: 01:153:14:25:48
Block: 884600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370727 RingCT/type: yes/0
Extra: 01286cac720035f8c3f0ff64a14d9c5293af7f395c866096151d67a90a3daa3b7202110000000633af99f4000000000000000000

1 output(s) for total of 0.719371107000 dcy

stealth address amount amount idx
00: 5062fefb673186a461337534ba9eb0f2884217dd4b7be46ce016c2bc17edc5a3 0.719371107000 1340345 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": 884610, "vin": [ { "gen": { "height": 884600 } } ], "vout": [ { "amount": 719371107, "target": { "key": "5062fefb673186a461337534ba9eb0f2884217dd4b7be46ce016c2bc17edc5a3" } } ], "extra": [ 1, 40, 108, 172, 114, 0, 53, 248, 195, 240, 255, 100, 161, 77, 156, 82, 147, 175, 127, 57, 92, 134, 96, 150, 21, 29, 103, 169, 10, 61, 170, 59, 114, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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