Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf535c0f019cdc25d29109e237276aaf420989ed4d58a2a9a5cf4a685612fd7

Tx prefix hash: 289ded0ae7aad7557780e064409f061fb9ab29d5f3cf73077c844615d26043b3
Tx public key: 9832294a213d2e793f7081026ecb8af5422f299bae308c15a8caf52f787125e1
Timestamp: 1722684953 Timestamp [UCT]: 2024-08-03 11:35:53 Age [y:d:h:m:s]: 00:174:01:45:33
Block: 1079811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124499 RingCT/type: yes/0
Extra: 019832294a213d2e793f7081026ecb8af5422f299bae308c15a8caf52f787125e1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa1d7dd3aff26be91dd0b4f51c8eee7213dd583fb8a613e261bb70ed82588993 0.600000000000 1552928 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": 1079821, "vin": [ { "gen": { "height": 1079811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa1d7dd3aff26be91dd0b4f51c8eee7213dd583fb8a613e261bb70ed82588993" } } ], "extra": [ 1, 152, 50, 41, 74, 33, 61, 46, 121, 63, 112, 129, 2, 110, 203, 138, 245, 66, 47, 41, 155, 174, 48, 140, 21, 168, 202, 245, 47, 120, 113, 37, 225, 2, 17, 0, 0, 0, 4, 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