Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5717ec5a0f69be8a4f927a7cedc8374fc0a063b2b072a5c408aa37a83d61fb45

Tx prefix hash: 937ff4fdf26fef66df2ee5e59c1946ae4a158866f6bdeae29c7ffaef2d4e2450
Tx public key: 08a5e226cdf3e30e7422cb3d865fc737e4dcba5575cf80ebe42ac78e631cc7e0
Timestamp: 1695939399 Timestamp [UCT]: 2023-09-28 22:16:39 Age [y:d:h:m:s]: 01:257:15:29:07
Block: 858288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445189 RingCT/type: yes/0
Extra: 0108a5e226cdf3e30e7422cb3d865fc737e4dcba5575cf80ebe42ac78e631cc7e002110000000975e3f0e9000000000000000000

1 output(s) for total of 0.879297034000 dcy

stealth address amount amount idx
00: e287c9ea16f9d778dab9eed9d2aee0a04ec731f36abc76f0afb13f4c72d4070c 0.879297034000 1312456 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": 858298, "vin": [ { "gen": { "height": 858288 } } ], "vout": [ { "amount": 879297034, "target": { "key": "e287c9ea16f9d778dab9eed9d2aee0a04ec731f36abc76f0afb13f4c72d4070c" } } ], "extra": [ 1, 8, 165, 226, 38, 205, 243, 227, 14, 116, 34, 203, 61, 134, 95, 199, 55, 228, 220, 186, 85, 117, 207, 128, 235, 228, 42, 199, 142, 99, 28, 199, 224, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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