Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13b19b70d152710c9c71de2844d4480b59f325324d84fa3115b1118331c9598e

Tx prefix hash: 9f29c7782a36f67a1bb597a836f9c6ca02b530d463924e32c3503eee46ac7432
Tx public key: 55f001b64ce7e2cfd8dc2a528f803aa5c104c616be49594275fb3f4794d5416a
Timestamp: 1722769601 Timestamp [UCT]: 2024-08-04 11:06:41 Age [y:d:h:m:s]: 00:277:22:19:29
Block: 1080514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198553 RingCT/type: yes/0
Extra: 0155f001b64ce7e2cfd8dc2a528f803aa5c104c616be49594275fb3f4794d5416a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 860bca023a2232dcc378e7ee0b9c187d93008ba29cfd0df00dbd932da79d5c38 0.600000000000 1553903 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": 1080524, "vin": [ { "gen": { "height": 1080514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "860bca023a2232dcc378e7ee0b9c187d93008ba29cfd0df00dbd932da79d5c38" } } ], "extra": [ 1, 85, 240, 1, 182, 76, 231, 226, 207, 216, 220, 42, 82, 143, 128, 58, 165, 193, 4, 198, 22, 190, 73, 89, 66, 117, 251, 63, 71, 148, 213, 65, 106, 2, 17, 0, 0, 0, 5, 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