Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2a216064b3e8e9279a1fbb2d47f5c9b91c3a7ce1681b9e3ccb130dc0abc9bec

Tx prefix hash: 5a67596bd4649fdceef4afe014ab18100467c628900f684ff83dfc80f80d22c5
Tx public key: 2f1b02bc09772cb0c8206c44d2d5e9cff5b5a6a8e1e00427d19c3fcb03d976ca
Timestamp: 1728892716 Timestamp [UCT]: 2024-10-14 07:58:36 Age [y:d:h:m:s]: 00:102:00:36:12
Block: 1131289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72873 RingCT/type: yes/0
Extra: 012f1b02bc09772cb0c8206c44d2d5e9cff5b5a6a8e1e00427d19c3fcb03d976ca021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fa1a1483215552919b70f253988747c24cfe043f1e2d409a42d9e1ba3fac3ab 0.600000000000 1614176 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": 1131299, "vin": [ { "gen": { "height": 1131289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fa1a1483215552919b70f253988747c24cfe043f1e2d409a42d9e1ba3fac3ab" } } ], "extra": [ 1, 47, 27, 2, 188, 9, 119, 44, 176, 200, 32, 108, 68, 210, 213, 233, 207, 245, 181, 166, 168, 225, 224, 4, 39, 209, 156, 63, 203, 3, 217, 118, 202, 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