Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f7a85df103223514d4b1234ae4db40de0ccaf5fa6917d03abb5fc239147d8a

Tx prefix hash: eb4bfbc9489ae8c22b7fc7c5866ae6c1e14bbfb58b30cb10e1fb535840bb0c8a
Tx public key: 5ddbaf0cc5068ef94236588be9079a7674a0e14baa4d1b4eee280843dbb0a0a4
Timestamp: 1736584082 Timestamp [UCT]: 2025-01-11 08:28:02 Age [y:d:h:m:s]: 00:070:11:38:42
Block: 1194909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50150 RingCT/type: yes/0
Extra: 015ddbaf0cc5068ef94236588be9079a7674a0e14baa4d1b4eee280843dbb0a0a4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb7d34ce8f635781af83350907ac53cf29c69ca738798c6ee50d969c7ade384 0.600000000000 1681488 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": 1194919, "vin": [ { "gen": { "height": 1194909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb7d34ce8f635781af83350907ac53cf29c69ca738798c6ee50d969c7ade384" } } ], "extra": [ 1, 93, 219, 175, 12, 197, 6, 142, 249, 66, 54, 88, 139, 233, 7, 154, 118, 116, 160, 225, 75, 170, 77, 27, 78, 238, 40, 8, 67, 219, 176, 160, 164, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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