Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f81615e64e23b2ff1a27d5ee4430a6cbe16ca46ac7e054eb16ba86a26a522ca0

Tx prefix hash: 2d1e18c465bcb9190ee66e5276b160c91bce796deb97a612e4bd5069f22c9430
Tx public key: 2c7e3d4743d96860d44eb2ed85db8fffba0aaf5a04d30cadbaf69f5a5988ee32
Timestamp: 1705106658 Timestamp [UCT]: 2024-01-13 00:44:18 Age [y:d:h:m:s]: 00:320:10:50:56
Block: 934062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229463 RingCT/type: yes/0
Extra: 012c7e3d4743d96860d44eb2ed85db8fffba0aaf5a04d30cadbaf69f5a5988ee3202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da2783bb55c1623d999f525c2faf5da44cbc5731da2f4c37bc0c2f610e27937 0.600000000000 1392048 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": 934072, "vin": [ { "gen": { "height": 934062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da2783bb55c1623d999f525c2faf5da44cbc5731da2f4c37bc0c2f610e27937" } } ], "extra": [ 1, 44, 126, 61, 71, 67, 217, 104, 96, 212, 78, 178, 237, 133, 219, 143, 255, 186, 10, 175, 90, 4, 211, 12, 173, 186, 246, 159, 90, 89, 136, 238, 50, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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