Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c7893816f8c034127bef4e01c2bfa4e899d6e405d2db838061dab25623194c5

Tx prefix hash: d8682e00032a38f379813320a50c719cf3a587eb5c63fd1538c685273869cc4a
Tx public key: e7a9f6d723bf42b1f03a201bdb9cc15aeb50f382442f3897cbd44fb1ae899ff2
Timestamp: 1729005431 Timestamp [UCT]: 2024-10-15 15:17:11 Age [y:d:h:m:s]: 00:210:21:03:43
Block: 1132223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150519 RingCT/type: yes/0
Extra: 01e7a9f6d723bf42b1f03a201bdb9cc15aeb50f382442f3897cbd44fb1ae899ff2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a1941bf78d0c4e4cb50a561217b3fffe942c46336e1384d29ec05ab28b3e522 0.600000000000 1615136 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": 1132233, "vin": [ { "gen": { "height": 1132223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a1941bf78d0c4e4cb50a561217b3fffe942c46336e1384d29ec05ab28b3e522" } } ], "extra": [ 1, 231, 169, 246, 215, 35, 191, 66, 177, 240, 58, 32, 27, 219, 156, 193, 90, 235, 80, 243, 130, 68, 47, 56, 151, 203, 212, 79, 177, 174, 137, 159, 242, 2, 17, 0, 0, 0, 3, 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