Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78de9fac3bce7b1086c4bdeb2fe7fe5680c4585d6bb7f1109018d055120c4730

Tx prefix hash: 611bfc99daf44b22b999cfce8e4b74de178dd941160230935f9d942c433e3176
Tx public key: b5aebd7a59ed821e0a2e9c812545fc9b04800fe2e03a76abfe737aecefb66d6d
Timestamp: 1726410331 Timestamp [UCT]: 2024-09-15 14:25:31 Age [y:d:h:m:s]: 00:208:21:02:05
Block: 1110703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149111 RingCT/type: yes/0
Extra: 01b5aebd7a59ed821e0a2e9c812545fc9b04800fe2e03a76abfe737aecefb66d6d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a05b3a6e2e079b9a41495ddc6c46051d75d0acb34a37879b518713fccdc586dc 0.600000000000 1589402 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": 1110713, "vin": [ { "gen": { "height": 1110703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a05b3a6e2e079b9a41495ddc6c46051d75d0acb34a37879b518713fccdc586dc" } } ], "extra": [ 1, 181, 174, 189, 122, 89, 237, 130, 30, 10, 46, 156, 129, 37, 69, 252, 155, 4, 128, 15, 226, 224, 58, 118, 171, 254, 115, 122, 236, 239, 182, 109, 109, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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