Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d411c293122bc4f25b51f52b31225c775c3ff9a532b9e13be9ee79b46240a2

Tx prefix hash: 1f1720bb60f3ba8beabe43674aa32c7c601fe225b2f5dc06a50716fe3e9def06
Tx public key: fba4c77e86be28f8f783628ced6a1dff33aee673cd9a4993116673623a9cb4e5
Timestamp: 1720513003 Timestamp [UCT]: 2024-07-09 08:16:43 Age [y:d:h:m:s]: 00:287:19:20:42
Block: 1061815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205629 RingCT/type: yes/0
Extra: 01fba4c77e86be28f8f783628ced6a1dff33aee673cd9a4993116673623a9cb4e502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 019ad34d8379dfd2d76fbf22221f7824d4c788e5d2032ce6ed235e48d0786999 0.600000000000 1532310 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": 1061825, "vin": [ { "gen": { "height": 1061815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "019ad34d8379dfd2d76fbf22221f7824d4c788e5d2032ce6ed235e48d0786999" } } ], "extra": [ 1, 251, 164, 199, 126, 134, 190, 40, 248, 247, 131, 98, 140, 237, 106, 29, 255, 51, 174, 230, 115, 205, 154, 73, 147, 17, 102, 115, 98, 58, 156, 180, 229, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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