Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd6a4ad6d4a6f6c7c04eef23ced3024c60e9fb50fb8521454df4896132bc694

Tx prefix hash: a6ac62d7219fd517596fd394fcc8f33cbdfc33ba203b4efdf8d935bb95d82319
Tx public key: 7ae54a0aea374349ce3d8b5ddb4bee6bd5a842d5157a55cacd006ecd438cec93
Timestamp: 1676397658 Timestamp [UCT]: 2023-02-14 18:00:58 Age [y:d:h:m:s]: 02:073:14:18:15
Block: 696970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574198 RingCT/type: yes/0
Extra: 017ae54a0aea374349ce3d8b5ddb4bee6bd5a842d5157a55cacd006ecd438cec9302110000000d835e4d22000000000000000000

1 output(s) for total of 3.010571748000 dcy

stealth address amount amount idx
00: 3b75b5966fae0b64223501c77b7636de111b7159be35bcbf043afa7bd129c0cd 3.010571748000 1140033 of 0

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": 696980, "vin": [ { "gen": { "height": 696970 } } ], "vout": [ { "amount": 3010571748, "target": { "key": "3b75b5966fae0b64223501c77b7636de111b7159be35bcbf043afa7bd129c0cd" } } ], "extra": [ 1, 122, 229, 74, 10, 234, 55, 67, 73, 206, 61, 139, 93, 219, 75, 238, 107, 213, 168, 66, 213, 21, 122, 85, 202, 205, 0, 110, 205, 67, 140, 236, 147, 2, 17, 0, 0, 0, 13, 131, 94, 77, 34, 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