Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14110480b1f24174c34d6683564fdf94e2537879a9ed245ff96a933005441447

Tx prefix hash: 287e945c4ab24b8bf6960b1ff065a87a05b2eea8fc203a0ba6399853e246335b
Tx public key: f27f79c5d0fe9d20591555c004dc65049b598ccd393afe9f3dcb75f580f1bae4
Timestamp: 1727350114 Timestamp [UCT]: 2024-09-26 11:28:34 Age [y:d:h:m:s]: 00:189:01:40:27
Block: 1118494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134931 RingCT/type: yes/0
Extra: 01f27f79c5d0fe9d20591555c004dc65049b598ccd393afe9f3dcb75f580f1bae4021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59ff7e1671f0ba3fadfe80e91c9359d931f0c98f57519a96de3d26729708112d 0.600000000000 1599707 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": 1118504, "vin": [ { "gen": { "height": 1118494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59ff7e1671f0ba3fadfe80e91c9359d931f0c98f57519a96de3d26729708112d" } } ], "extra": [ 1, 242, 127, 121, 197, 208, 254, 157, 32, 89, 21, 85, 192, 4, 220, 101, 4, 155, 89, 140, 205, 57, 58, 254, 159, 61, 203, 117, 245, 128, 241, 186, 228, 2, 17, 0, 0, 0, 9, 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