Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27da2a33352edd0590978ee24d0e7792574c97a9121171a8c60845e4288064f7

Tx prefix hash: 223da7c6faa49aabe199c706218c2e79609446b2cb78a6f7fb1c1eda7172b953
Tx public key: f8081a7f297caafa9d976e48e9374f4360f6b0e6ac3cabb52c05e27f56fef3ef
Timestamp: 1704365087 Timestamp [UCT]: 2024-01-04 10:44:47 Age [y:d:h:m:s]: 01:119:14:09:19
Block: 927941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346575 RingCT/type: yes/0
Extra: 01f8081a7f297caafa9d976e48e9374f4360f6b0e6ac3cabb52c05e27f56fef3ef021100000007e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6572d8ce42512341c27ca2a731e6a521ea28ab53f7eb2a78cae35f47b9a1595f 0.600000000000 1385789 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": 927951, "vin": [ { "gen": { "height": 927941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6572d8ce42512341c27ca2a731e6a521ea28ab53f7eb2a78cae35f47b9a1595f" } } ], "extra": [ 1, 248, 8, 26, 127, 41, 124, 170, 250, 157, 151, 110, 72, 233, 55, 79, 67, 96, 246, 176, 230, 172, 60, 171, 181, 44, 5, 226, 127, 86, 254, 243, 239, 2, 17, 0, 0, 0, 7, 228, 187, 107, 131, 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