Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 758ed9ffe8a77a60e099e2ec28a3071541fd9e867717f9b89ecfff02e368dc0c

Tx prefix hash: 164de19d6b4bdd7b3e89220f9a2080b20317a1dbf6af43c14c1bc77dfdb2b574
Tx public key: bc9ae2df3f015913aed50bd80174d4791eaa55e6a276bb6fece55bec335640f1
Timestamp: 1704411654 Timestamp [UCT]: 2024-01-04 23:40:54 Age [y:d:h:m:s]: 01:052:23:42:21
Block: 928300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298957 RingCT/type: yes/0
Extra: 01bc9ae2df3f015913aed50bd80174d4791eaa55e6a276bb6fece55bec335640f102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60c5843e476ca42963bc00be30270c25b57a37811e9a5a5695ed40b690262218 0.600000000000 1386158 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": 928310, "vin": [ { "gen": { "height": 928300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60c5843e476ca42963bc00be30270c25b57a37811e9a5a5695ed40b690262218" } } ], "extra": [ 1, 188, 154, 226, 223, 63, 1, 89, 19, 174, 213, 11, 216, 1, 116, 212, 121, 30, 170, 85, 230, 162, 118, 187, 111, 236, 229, 91, 236, 51, 86, 64, 241, 2, 17, 0, 0, 0, 6, 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