Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec97513a79e762e37bd120513951c967b119c284271ec1f0d58066264c5b5f6

Tx prefix hash: 06f02015c8780c5eb74b63a7fb9c90f270f47253dadb6d42b0a2ed407f9db94d
Tx public key: 41a3e13a1ffec6f89e8d5b33a4b8bc81fc6e9ff271532eefb7f2d93b083c9a32
Timestamp: 1722802571 Timestamp [UCT]: 2024-08-04 20:16:11 Age [y:d:h:m:s]: 00:242:05:54:21
Block: 1080789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173019 RingCT/type: yes/0
Extra: 0141a3e13a1ffec6f89e8d5b33a4b8bc81fc6e9ff271532eefb7f2d93b083c9a3202110000001f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba278e5b4bb9e063aea23f006623d3737e71a5bb8aede9bb1a629845dd8960df 0.600000000000 1554282 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": 1080799, "vin": [ { "gen": { "height": 1080789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba278e5b4bb9e063aea23f006623d3737e71a5bb8aede9bb1a629845dd8960df" } } ], "extra": [ 1, 65, 163, 225, 58, 31, 254, 198, 248, 158, 141, 91, 51, 164, 184, 188, 129, 252, 110, 159, 242, 113, 83, 46, 239, 183, 242, 217, 59, 8, 60, 154, 50, 2, 17, 0, 0, 0, 31, 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