Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85db2971530ca0e05a266aa1d13ffb3dc517dac152051be22e30efba6eab213

Tx prefix hash: eb736b6d8db7c2556a864803d6d0e5e87d81c0619096f4898b69673a04bd453e
Tx public key: 40b022349cc5a47991bdd1c4e8823c09c33cb288d4d3506ca066e271b83869e3
Timestamp: 1704191437 Timestamp [UCT]: 2024-01-02 10:30:37 Age [y:d:h:m:s]: 01:320:11:52:49
Block: 926487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487897 RingCT/type: yes/0
Extra: 0140b022349cc5a47991bdd1c4e8823c09c33cb288d4d3506ca066e271b83869e30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4069194657e4e9770d32ad48274b4928a294c96d74fad01a5b4cd5ffa3b99d7a 0.600000000000 1384273 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": 926497, "vin": [ { "gen": { "height": 926487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4069194657e4e9770d32ad48274b4928a294c96d74fad01a5b4cd5ffa3b99d7a" } } ], "extra": [ 1, 64, 176, 34, 52, 156, 197, 164, 121, 145, 189, 209, 196, 232, 130, 60, 9, 195, 60, 178, 136, 212, 211, 80, 108, 160, 102, 226, 113, 184, 56, 105, 227, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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