Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d74ecf1cd6ea304a28d3db4307a3d31722f86942485a92877bb02ecced578cb2

Tx prefix hash: 4454bbf006b374fa27156570bd7f3cdd0149ed137181d773a5cf9b34dcf14e94
Tx public key: fd9b213291166347539ff8e9cee9bad89fd094bdd4f6cd21c7d9ae5fa0c12f06
Timestamp: 1736136834 Timestamp [UCT]: 2025-01-06 04:13:54 Age [y:d:h:m:s]: 00:298:12:06:29
Block: 1191211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210836 RingCT/type: yes/0
Extra: 01fd9b213291166347539ff8e9cee9bad89fd094bdd4f6cd21c7d9ae5fa0c12f0602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428c231f8366f4051155f38f10f65df0aed042b7c8164d4df9f29c7f3ac2bb44 0.600000000000 1677734 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": 1191221, "vin": [ { "gen": { "height": 1191211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428c231f8366f4051155f38f10f65df0aed042b7c8164d4df9f29c7f3ac2bb44" } } ], "extra": [ 1, 253, 155, 33, 50, 145, 22, 99, 71, 83, 159, 248, 233, 206, 233, 186, 216, 159, 208, 148, 189, 212, 246, 205, 33, 199, 217, 174, 95, 160, 193, 47, 6, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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