Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee179c96138b133c7f9b26f007f19f730218723e1ba0f5b50eb32de36073a0f4

Tx prefix hash: 3a31a0e480d5d32790bc388bbdc363b7e8c4b9c1bb810bdbfb99deec90bf4f7f
Tx public key: 4b3b00c0c88cfa22bc299a19abb461eb7ccc5678452f54768daac825e89c4f56
Timestamp: 1750174350 Timestamp [UCT]: 2025-06-17 15:32:30 Age [y:d:h:m:s]: 00:151:12:58:35
Block: 1307041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106098 RingCT/type: yes/0
Extra: 014b3b00c0c88cfa22bc299a19abb461eb7ccc5678452f54768daac825e89c4f56021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b2a4548a95bb230dc1f6ee70526dc9aad3aa216205772475f7fcbcdb4df7d3c 0.600000000000 1794650 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": 1307051, "vin": [ { "gen": { "height": 1307041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b2a4548a95bb230dc1f6ee70526dc9aad3aa216205772475f7fcbcdb4df7d3c" } } ], "extra": [ 1, 75, 59, 0, 192, 200, 140, 250, 34, 188, 41, 154, 25, 171, 180, 97, 235, 124, 204, 86, 120, 69, 47, 84, 118, 141, 170, 200, 37, 232, 156, 79, 86, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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