Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438c35ed6e9972d98ee4dc304d87968deeff56dfa826d27f44aee12d46a10d8e

Tx prefix hash: 6ae81e344759722cd0bbd4182b0b4a387f152cbe2d842d104d9ba9711b129fec
Tx public key: 0618e0558c794b603c8f3c86841516995d5dcaa18b9376fee1b516398cd2ac7b
Timestamp: 1699894407 Timestamp [UCT]: 2023-11-13 16:53:27 Age [y:d:h:m:s]: 01:124:19:16:50
Block: 890876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350388 RingCT/type: yes/0
Extra: 010618e0558c794b603c8f3c86841516995d5dcaa18b9376fee1b516398cd2ac7b02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.685737640000 dcy

stealth address amount amount idx
00: cac8841f45fb4c18e214c94a4bd4a6678198fd9198830cfe8fede5ec47697c98 0.685737640000 1346907 of 0

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": 890886, "vin": [ { "gen": { "height": 890876 } } ], "vout": [ { "amount": 685737640, "target": { "key": "cac8841f45fb4c18e214c94a4bd4a6678198fd9198830cfe8fede5ec47697c98" } } ], "extra": [ 1, 6, 24, 224, 85, 140, 121, 75, 96, 60, 143, 60, 134, 132, 21, 22, 153, 93, 93, 202, 161, 139, 147, 118, 254, 225, 181, 22, 57, 140, 210, 172, 123, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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