Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c3771e2613b4ab73dcd6663491a0b30cbc4fbff1d146269597af4650217b787

Tx prefix hash: 0c5cd1ffa35d039ab91dc10c700dbbe83c1ac6a57e9ef12a5af08cf8e0d7078a
Tx public key: 40082be8864f8d55bdf505417c69d2e3c03152cf4a3d79ae3d5f1854605725a1
Timestamp: 1723172876 Timestamp [UCT]: 2024-08-09 03:07:56 Age [y:d:h:m:s]: 00:168:14:19:15
Block: 1083852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120576 RingCT/type: yes/0
Extra: 0140082be8864f8d55bdf505417c69d2e3c03152cf4a3d79ae3d5f1854605725a102110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f45fa5d067eb285786abca67e8fc2edb1248bdbd536a100bff091f4a8caa85c4 0.600000000000 1557923 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": 1083862, "vin": [ { "gen": { "height": 1083852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f45fa5d067eb285786abca67e8fc2edb1248bdbd536a100bff091f4a8caa85c4" } } ], "extra": [ 1, 64, 8, 43, 232, 134, 79, 141, 85, 189, 245, 5, 65, 124, 105, 210, 227, 192, 49, 82, 207, 74, 61, 121, 174, 61, 95, 24, 84, 96, 87, 37, 161, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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