Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93013bcc1b63198e88d4b8d871daa173d2be40554f88f507ceb8a3d17c2d244a

Tx prefix hash: 9a9baf3c16c304e819355b37337c2a85e906bdd4349cc5863e4c1d8e8e4a3984
Tx public key: 0542fa675b220108ff66fbc1b189ab1c5ca7c7f607e5912b911359a41ead4d44
Timestamp: 1730097550 Timestamp [UCT]: 2024-10-28 06:39:10 Age [y:d:h:m:s]: 00:209:02:33:54
Block: 1141194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149330 RingCT/type: yes/0
Extra: 010542fa675b220108ff66fbc1b189ab1c5ca7c7f607e5912b911359a41ead4d44021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 563a2bbd361396215df747fd38dafea6d9d48a928b86ee7ec9ede56d6798e472 0.600000000000 1625001 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": 1141204, "vin": [ { "gen": { "height": 1141194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "563a2bbd361396215df747fd38dafea6d9d48a928b86ee7ec9ede56d6798e472" } } ], "extra": [ 1, 5, 66, 250, 103, 91, 34, 1, 8, 255, 102, 251, 193, 177, 137, 171, 28, 92, 167, 199, 246, 7, 229, 145, 43, 145, 19, 89, 164, 30, 173, 77, 68, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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