Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ade3f5f4a49f041f693956372ffa9ae52aeb094f8e2c3d1a6ded7a2c3c84bd9

Tx prefix hash: 990339a4730873dd950945b83124a403e5640d0c15afdd9968619dcd9174da4a
Tx public key: 5ebc2dc2a046f14ee4f36fc7d77f5d96429e210d9df767c4a740f4689a4e536a
Timestamp: 1704272455 Timestamp [UCT]: 2024-01-03 09:00:55 Age [y:d:h:m:s]: 01:127:14:05:10
Block: 927168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352306 RingCT/type: yes/0
Extra: 015ebc2dc2a046f14ee4f36fc7d77f5d96429e210d9df767c4a740f4689a4e536a02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f34a812612d0e69f40dfd704140f683f8ecd5d812cace7a4fd2be725c94ae4 0.600000000000 1384972 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": 927178, "vin": [ { "gen": { "height": 927168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f34a812612d0e69f40dfd704140f683f8ecd5d812cace7a4fd2be725c94ae4" } } ], "extra": [ 1, 94, 188, 45, 194, 160, 70, 241, 78, 228, 243, 111, 199, 215, 127, 93, 150, 66, 158, 33, 13, 157, 247, 103, 196, 167, 64, 244, 104, 154, 78, 83, 106, 2, 17, 0, 0, 0, 10, 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