Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b579fa3be1a3de06c54e219ba9557185061a66f3facd429ae3a2847eb143887e

Tx prefix hash: 86b2057b7c625f9438ca440a5bca651c00a9f92912bfd49e36c36fb9f260b033
Tx public key: 30ee9080c563822dc60d8d33c690b04e0ccf2251c6eb67260fd5dc77f4cccd58
Timestamp: 1723049767 Timestamp [UCT]: 2024-08-07 16:56:07 Age [y:d:h:m:s]: 00:138:20:31:03
Block: 1082834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99353 RingCT/type: yes/0
Extra: 0130ee9080c563822dc60d8d33c690b04e0ccf2251c6eb67260fd5dc77f4cccd58021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8be8ff6b939b58f0f3cbd1e35b56af6008d181cb7129931951f3023af14247b 0.600000000000 1556669 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": 1082844, "vin": [ { "gen": { "height": 1082834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8be8ff6b939b58f0f3cbd1e35b56af6008d181cb7129931951f3023af14247b" } } ], "extra": [ 1, 48, 238, 144, 128, 197, 99, 130, 45, 198, 13, 141, 51, 198, 144, 176, 78, 12, 207, 34, 81, 198, 235, 103, 38, 15, 213, 220, 119, 244, 204, 205, 88, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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