Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772f29adf15bfb3f0a5cb37bbdc9dd7a2a1724f96fbfd808cbeb6629a5960f0d

Tx prefix hash: 03b54e7df12879a4526cba192a8150f8d661aa0874cb4b4ccc0d38b4de4e97b0
Tx public key: 311120d29be7367e728e89d57a55a06274e8c990d08b547e6d071b5f4e1db4e2
Timestamp: 1713604098 Timestamp [UCT]: 2024-04-20 09:08:18 Age [y:d:h:m:s]: 01:003:19:41:30
Block: 1004512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263687 RingCT/type: yes/0
Extra: 01311120d29be7367e728e89d57a55a06274e8c990d08b547e6d071b5f4e1db4e20211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 092902bfc1dc2d62e7625f7f3693686d497b568879148eba05778b9b29d59d03 0.600000000000 1465080 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": 1004522, "vin": [ { "gen": { "height": 1004512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "092902bfc1dc2d62e7625f7f3693686d497b568879148eba05778b9b29d59d03" } } ], "extra": [ 1, 49, 17, 32, 210, 155, 231, 54, 126, 114, 142, 137, 213, 122, 85, 160, 98, 116, 232, 201, 144, 208, 139, 84, 126, 109, 7, 27, 95, 78, 29, 180, 226, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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