Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c34ee36eb423f2a44047a292e16702a8e0e5d5a1d8b6dc135947048aa599529

Tx prefix hash: c1f518a262462c3cfce5accb10ac48e7b8ba5525f27ceba79bcd3c5e5006818f
Tx public key: c4d78ac09c608869540c77a30c000f07dbb367eb1d1dc8dabc66f18dd029f19c
Timestamp: 1731371425 Timestamp [UCT]: 2024-11-12 00:30:25 Age [y:d:h:m:s]: 00:138:07:50:50
Block: 1151729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98687 RingCT/type: yes/0
Extra: 01c4d78ac09c608869540c77a30c000f07dbb367eb1d1dc8dabc66f18dd029f19c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27a9e01a70f85e0763c7b36c5d6bbe497cceacb217cb978021ec37381ff25528 0.600000000000 1637310 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": 1151739, "vin": [ { "gen": { "height": 1151729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27a9e01a70f85e0763c7b36c5d6bbe497cceacb217cb978021ec37381ff25528" } } ], "extra": [ 1, 196, 215, 138, 192, 156, 96, 136, 105, 84, 12, 119, 163, 12, 0, 15, 7, 219, 179, 103, 235, 29, 29, 200, 218, 188, 102, 241, 141, 208, 41, 241, 156, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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