Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 245585bbcccce1378ce68ff66e25f3c20c2aaf07e0f8bc945413104fe10fb668

Tx prefix hash: 22f0e7adea1e77d30a96b23197c67cd1070d49846be442f5f4210787cee188a3
Tx public key: 445dc59330accd82761aff8fc68d56f6af813dc80a0041d2164cfb596e9882f2
Timestamp: 1723797810 Timestamp [UCT]: 2024-08-16 08:43:30 Age [y:d:h:m:s]: 00:210:03:32:47
Block: 1089037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150084 RingCT/type: yes/0
Extra: 01445dc59330accd82761aff8fc68d56f6af813dc80a0041d2164cfb596e9882f2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae8fd5b064b82a48bbbacf6b37b6f8d5242d4ea87fb736b9a8fdbdf3c973e364 0.600000000000 1563656 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": 1089047, "vin": [ { "gen": { "height": 1089037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae8fd5b064b82a48bbbacf6b37b6f8d5242d4ea87fb736b9a8fdbdf3c973e364" } } ], "extra": [ 1, 68, 93, 197, 147, 48, 172, 205, 130, 118, 26, 255, 143, 198, 141, 86, 246, 175, 129, 61, 200, 10, 0, 65, 210, 22, 76, 251, 89, 110, 152, 130, 242, 2, 17, 0, 0, 0, 5, 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