Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e6d1aa255133cd4dce0361f010af406b8a5d5cfc5b15f8ceb2675b4af717be

Tx prefix hash: 4745ff11e2dc3e58e25993fe5e399fbb7eee9e85d4c735ed0b2cd802b1927254
Tx public key: 93106450fb5756319775e33be5751b67b4bdd364cf261238e16291f125540c79
Timestamp: 1747120573 Timestamp [UCT]: 2025-05-13 07:16:13 Age [y:d:h:m:s]: 00:139:11:26:15
Block: 1281863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97318 RingCT/type: yes/0
Extra: 0193106450fb5756319775e33be5751b67b4bdd364cf261238e16291f125540c790211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f428adf16d38ac75ffc54e6c3145c98cff8e7afda567cda862bde8c73c0245d2 0.600000000000 1769270 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": 1281873, "vin": [ { "gen": { "height": 1281863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f428adf16d38ac75ffc54e6c3145c98cff8e7afda567cda862bde8c73c0245d2" } } ], "extra": [ 1, 147, 16, 100, 80, 251, 87, 86, 49, 151, 117, 227, 59, 229, 117, 27, 103, 180, 189, 211, 100, 207, 38, 18, 56, 225, 98, 145, 241, 37, 84, 12, 121, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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