Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81c6b09700a7a7dc24e6e5a691dfb39dbc8893f8a46c0a96695fe5da11875bf8

Tx prefix hash: 897d095b3bccdd20138f57c1995ec53560058799e237ed86af64bb55b996548a
Tx public key: 2d55b5448a1b3477d7cc26b8bd875809474df69ac72f7a32214025806b5ffdf8
Timestamp: 1704733418 Timestamp [UCT]: 2024-01-08 17:03:38 Age [y:d:h:m:s]: 01:099:19:17:46
Block: 930976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332441 RingCT/type: yes/0
Extra: 012d55b5448a1b3477d7cc26b8bd875809474df69ac72f7a32214025806b5ffdf802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14764a10e44616f11fa9eae6bcafe487ee9ae18dc1f005f184d15ba4117127f3 0.600000000000 1388868 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": 930986, "vin": [ { "gen": { "height": 930976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14764a10e44616f11fa9eae6bcafe487ee9ae18dc1f005f184d15ba4117127f3" } } ], "extra": [ 1, 45, 85, 181, 68, 138, 27, 52, 119, 215, 204, 38, 184, 189, 135, 88, 9, 71, 77, 246, 154, 199, 47, 122, 50, 33, 64, 37, 128, 107, 95, 253, 248, 2, 17, 0, 0, 0, 2, 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