Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bb97e2ac9ec3ff8b45a5034f4d1b23bbea0a8e28d2194e54a0aafff24f71451

Tx prefix hash: 93ce53b109769c6a0dde69d51a5861bf61011ac0e29c0df1414ad167f7279a3b
Tx public key: 72aadbc1a1a7d4994c40d50bc9ab83cd7ecfec666507874fc14b13f7a613dc48
Timestamp: 1719521946 Timestamp [UCT]: 2024-06-27 20:59:06 Age [y:d:h:m:s]: 00:357:23:13:25
Block: 1053587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255682 RingCT/type: yes/0
Extra: 0172aadbc1a1a7d4994c40d50bc9ab83cd7ecfec666507874fc14b13f7a613dc480211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd65a9a821d71c77718d8faebb5903d13fd6bfe3a3a7fedcf8e196756f4f4ba8 0.600000000000 1523934 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": 1053597, "vin": [ { "gen": { "height": 1053587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd65a9a821d71c77718d8faebb5903d13fd6bfe3a3a7fedcf8e196756f4f4ba8" } } ], "extra": [ 1, 114, 170, 219, 193, 161, 167, 212, 153, 76, 64, 213, 11, 201, 171, 131, 205, 126, 207, 236, 102, 101, 7, 135, 79, 193, 75, 19, 247, 166, 19, 220, 72, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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