Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7488273521a29347e2c22b7e6fc895a7bd9ecd50d5cb0791f600e995218a96dc

Tx prefix hash: ff49a70c7f15a5c534cb615e07fe1a029d9b32bd481d9b1cea4335856c4ce872
Tx public key: 00e7af0ea945bd52d16005b227e59ae42c8ccf4aaf336f2ac158d8ad4035603b
Timestamp: 1761779280 Timestamp [UCT]: 2025-10-29 23:08:00 Age [y:d:h:m:s]: 00:007:06:47:39
Block: 1400817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5195 RingCT/type: yes/0
Extra: 0100e7af0ea945bd52d16005b227e59ae42c8ccf4aaf336f2ac158d8ad4035603b02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7613c1cd8df310f6930c91bea6ee959f185c5c023fdaa67380fd083381d9cad2 0.600000000000 1889136 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": 1400827, "vin": [ { "gen": { "height": 1400817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7613c1cd8df310f6930c91bea6ee959f185c5c023fdaa67380fd083381d9cad2" } } ], "extra": [ 1, 0, 231, 175, 14, 169, 69, 189, 82, 209, 96, 5, 178, 39, 229, 154, 228, 44, 140, 207, 74, 175, 51, 111, 42, 193, 88, 216, 173, 64, 53, 96, 59, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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