Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e71169822a4a29dad2c75aeb0aa69ce3ebcfd3015be8f2569be8bd5a9672c40

Tx prefix hash: 53fc7a7ca5eee6259c05b20fa9250b6c3ba795f52a628224584cf1d84d040bcb
Tx public key: af0dcf97490b8a91b5cf8bdd9a50f8d407cfb8dc160097b07a564b608d1f6e7b
Timestamp: 1734872812 Timestamp [UCT]: 2024-12-22 13:06:52 Age [y:d:h:m:s]: 00:103:04:20:01
Block: 1180764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73503 RingCT/type: yes/0
Extra: 01af0dcf97490b8a91b5cf8bdd9a50f8d407cfb8dc160097b07a564b608d1f6e7b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e6fb6dfb216d7e28ba6179a46c473ae1c981f33ab0db46aa4c5f0a841bc6da1 0.600000000000 1667177 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": 1180774, "vin": [ { "gen": { "height": 1180764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e6fb6dfb216d7e28ba6179a46c473ae1c981f33ab0db46aa4c5f0a841bc6da1" } } ], "extra": [ 1, 175, 13, 207, 151, 73, 11, 138, 145, 181, 207, 139, 221, 154, 80, 248, 212, 7, 207, 184, 220, 22, 0, 151, 176, 122, 86, 75, 96, 141, 31, 110, 123, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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