Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e1d82dbd4070c902e924778e2c2ecc8372b774fcca72d396c1a769ccde922d

Tx prefix hash: 6570a48b4593bda2fd0df2cf6bfd3f2248592df594d13e5339ee3c1fa8b78506
Tx public key: 366c73df86ba67dd910f322a00f1bceac1bcf66ef268928b64a4ebf3500c50a2
Timestamp: 1764163239 Timestamp [UCT]: 2025-11-26 13:20:39 Age [y:d:h:m:s]: 00:000:19:33:45
Block: 1420558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593 RingCT/type: yes/0
Extra: 01366c73df86ba67dd910f322a00f1bceac1bcf66ef268928b64a4ebf3500c50a2021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ab57894c091b01b08ee35a78740c3f51a5a7b69541257d9325a0e7ee0352f1 0.600000000000 1909103 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": 1420568, "vin": [ { "gen": { "height": 1420558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ab57894c091b01b08ee35a78740c3f51a5a7b69541257d9325a0e7ee0352f1" } } ], "extra": [ 1, 54, 108, 115, 223, 134, 186, 103, 221, 145, 15, 50, 42, 0, 241, 188, 234, 193, 188, 246, 110, 242, 104, 146, 139, 100, 164, 235, 243, 80, 12, 80, 162, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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